Hi, I have a Exch 2003 Ent with spk2 where users who send e-mails trought OWA to a specific domain (like @hotmail.com for example) works fine and SMTP LOG shows the following: 2010-05-20 17:39:34 208.84.244.133 OutboundConnectionResponse SMTPSVC1 MAILSERVER - 25 - - 220+quesnel.terra.com+ESMTP 0 0 27 0 235 SMTP - - - - 2010-05-20 17:39:34 208.84.244.133 OutboundConnectionCommand SMTPSVC1 MAILSERVER - 25 EHLO - qubomail1.qubo.com.br 0 0 4 0 235 SMTP - - - - 2010-05-20 17:39:34 208.84.244.133 OutboundConnectionResponse SMTPSVC1 MAILSERVER - 25 - - 250-quesnel.terra.com 0 0 21 0 422 SMTP - - - - 2010-05-20 17:39:34 208.84.244.133 OutboundConnectionCommand SMTPSVC1 MAILSERVER - 25 MAIL - FROM:<duetto@pimenteladvogados.com.br>+SIZE=1311 0 0 4 0 438 SMTP - - - - 2010-05-20 17:39:36 208.84.244.133 OutboundConnectionResponse SMTPSVC1 MAILSERVER - 25 - - 250+2.1.0+Ok 0 0 12 0 2657 SMTP - - - - 2010-05-20 17:39:36 208.84.244.133 OutboundConnectionCommand SMTPSVC1 MAILSERVER - 25 RCPT - TO:<danko@terra.com.br> 0 0 4 0 2657 SMTP - - - - 2010-05-20 17:39:36 208.84.244.133 OutboundConnectionResponse SMTPSVC1 MAILSERVER - 25 - - 250+2.1.5+Ok 0 0 12 0 2860 SMTP - - - - 2010-05-20 17:39:36 208.84.244.133 OutboundConnectionCommand SMTPSVC1 MAILSERVER - 25 DATA - - 0 0 4 0 2860 SMTP - - - - But when external users using MS OUTLOOK with AUTHENTICATED SMTP sends e-mail, the log show 'COMPUTER1' and send EHLO as 'COMPUTER1' instead 'OutboundConnection' with FQDN of server, as specified on External SMTP Connector name... Why?????? * My users is facing problems to send e-mails!!!!!!

On Thu, 20 May 2010 17:51:02 +0000, Renato Jr wrote: >Hi, I have a Exch 2003 Ent with spk2 where users who send e-mails trought OWA to a specific domain (like @hotmail.com for example) works fine and SMTP LOG shows the following: >2010-05-20 17:39:34 208.84.244.133 OutboundConnectionResponse SMTPSVC1 MAILSERVER - 25 - - 220+quesnel.terra.com+ESMTP 0 0 27 0 235 SMTP - - - - >2010-05-20 17:39:34 208.84.244.133 OutboundConnectionCommand SMTPSVC1 MAILSERVER - 25 EHLO - qubomail1.qubo.com.br 0 0 4 0 235 SMTP - - - - >2010-05-20 17:39:34 208.84.244.133 OutboundConnectionResponse SMTPSVC1 MAILSERVER - 25 - - 250-quesnel.terra.com 0 0 21 0 422 SMTP - - - - >2010-05-20 17:39:34 208.84.244.133 OutboundConnectionCommand SMTPSVC1 MAILSERVER - 25 MAIL - FROM:<duetto@pimenteladvogados.com.br>+SIZE=1311 0 0 4 0 438 SMTP - - - - >2010-05-20 17:39:36 208.84.244.133 OutboundConnectionResponse SMTPSVC1 MAILSERVER - 25 - - 250+2.1.0+Ok 0 0 12 0 2657 SMTP - - - - >2010-05-20 17:39:36 208.84.244.133 OutboundConnectionCommand SMTPSVC1 MAILSERVER - 25 RCPT - >TO:<danko@terra.com.br> 0 0 4 0 2657 SMTP - - - - >2010-05-20 17:39:36 208.84.244.133 OutboundConnectionResponse SMTPSVC1 MAILSERVER - 25 - - 250+2.1.5+Ok 0 0 12 0 2860 SMTP - - - - >2010-05-20 17:39:36 208.84.244.133 OutboundConnectionCommand SMTPSVC1 MAILSERVER - 25 DATA - - 0 0 4 0 2860 SMTP - - - - > >But when external users using MS OUTLOOK with AUTHENTICATED SMTP sends e-mail, the log show 'COMPUTER1' and send EHLO as 'COMPUTER1' instead 'OutboundConnection' with FQDN of server, as specified on External SMTP Connector name... Why?????? * My users is facing problems to send e-mails!!!!!! The log entries you provided are for outbound connections from your Exchange server to another machine. When some other machine sends e-mail to your machine the connection is no longer "outbound" so you shouldn't expect to see "OutboundConnection*" for the activity they generate. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Rich, I undestand and agree with you. But external users are facing problems because their e-mails goes as "EHLO COMPUTER1" and other SMTP Server cannot verify REVERSE - of course ... so the problem start and e-mails are tagged as 'possible spam'...

Have you had this problem earlier? Or just started? But basically your behavior is quite normal as your users connecting to the port 25 where you do the reverse lookup. Maybe some of these can solve the issue: A) Create new SMTP receiver on the E2003 server using another port or IP address and make other rules for that. B) Try do exclude the external users by the IP addresses, but I assume this might be mission impossible. C) Configure your clients so that they do have valid DNS records. D) Switch to use RPC over HTTPS. I feel that A is most easiest and fastest solution. B and C are just in case, you have plenty of time :D But D, that I assume is the best option.

On Fri, 21 May 2010 20:09:54 +0000, Renato Jr wrote: >I undestand and agree with you. But external users are facing problems because their e-mails goes as "EHLO COMPUTER1" and other SMTP Server cannot verify REVERSE - of course ... so the problem start and e-mails are tagged as 'possible spam'... So why not put the correct FWDN into the SMTP Virtual Server's property page? Your server should be identifying itself properly, anf the name should probably be the same one you nominated in your MX record. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Reneto, Try to configure your SMTP virtual server to use the IP address of your ISP's DNS server and see if the issue persists: 1. Open Exchange System Manager. Navigate to Administrative Groups, Site, Servers, Server name, Protocols, SMTP, Default SMTP Virtual Server, 2. Highlight Default SMTP Virtual Server, right click properties. 3. Go to the Delivery Tab, and click Advanced Button. 4. In the "Fully-qualified domain name: field, enter your fully qualified external domain name. This name must match the name that your users type when they configure their client software to deliver SMTP mail. 5. Click Configure next to Configure external DNS Servers. 6. Click Add, type the IP address of your ISP's DNS server, and then click OK. 7. Restart SMTP service.

Hi all, tks for reply. I have only 1 SMTP Virtual server on this server (fisically located at IDC) with FQDN since install... I´ll try to convert to RPC over HTTP or use another SMTP Virtual Server. * For users who use MS Outlook through MAPI or who use OWA e-mails outgoing works fine... tks a lot!

fisically lol.